Cerner Workflow System API - Implementation Template

Please review the prerequisite instructions to set up a System Account and App in Cerner.

Importing templates into Anypoint Studio

1. In Studio, click the Exchange X icon in the upper left of the taskbar.
2. Log in with your Anypoint Platform credentials.
3. Search for the template.
4. Click Open.

Running templates in Anypoint Studio

After you import your template into Studio, use the following configuration steps to run it.

Common configuration

• mule.env - sets the environment where the application is to be deployed. It should be configured in config-<mule.env>.yaml file. For a studio deployment, the recommended mule.env value is local
• mule.key - sets the encryption password to be used for encrypting secure properties. Update as needed
• api.baseurl - sets the base url of the api. Replace/override as needed when deploying to any environment. It should be configured in config-<mule.env>.yaml file. Default value is https://localhost:8082/api, when mule.env is local
• api.autoDiscoveryId should be configured in config-<mule.env>.yaml file.

Cerner Configuration

• cerner.tokenurl - sets the token url for Cerner. It should be configured in config-<mule.env>.yaml file
• cerner.baseurl - sets the base url for Cerner R4 requests. It should be configured in config-<mule.env>.yaml file
• cerner.scopes - set the scopes for the OAuth request to Cerner Token Url. Update the scopes as required for the operations. It should be configured in config-<mule.env>.yaml file
• cerner.clientId - sets the client id to be used for requests to Cerner Url. It should be configured in config-<mule.env>.yaml file
• cerner.clientSecret - sets the client secret to be used for requests to Cerner Url. It should be encrypted and configured in config-secured-<mule.env>.yaml file

Please refer to the attached link on how to secure the configuration properties.

HTTP Configuration

• https.host — sets the service host interface. It should be configured in config-<mule.env>.yaml file. (Defaults to 0.0.0.0 for all interfaces).
• https.port — sets the HTTPS service port number. It should be configured in config-<mule.env>.yaml file. (Default 8082).
• TLS Configuration - Keystore properties setup:
  • keystore.alias - sets the alias to the keystore. It should be configured in config-<mule.env>.yaml file.
  • keystore.path - sets the path to the key file. Key should be available in /src/main/resources/keystore. It should be configured in config-<mule.env>.yaml file.
  • keystore.keypass — sets keystore keypass to support HTTPS operation. It should be encrypted and configured in config-secured-<mule.env>.yaml file.
  • keystore.password— sets keystore password to support HTTPS operation. It should be encrypted and configured in config-secured-<mule.env>.yaml file.

Please refer to the attached link on how to generate the Keystore.

Run it

1. Right-click the template project folder.
2. Hover your mouse over 'Run as'.
3. Click Mule Application (configure).
4. Inside the dialog, select Environment and set the variable mule.env to the appropriate value (e.g., dev or local).
5. Inside the dialog, select Environment and set the variable mule.key to the property encryption key that you used to encrypt your secure properties.
6. Click Run.

Deployment instructions for CloudHub using provided scripts

Ensure the Maven profile CloudHub-HLS-DEV has been properly configured in your settings.xml file. Reference can be found by downloading the Accelerator Common Resources asset. Additional instructions are available in the Getting Started with MuleSoft Accelerators - Build Environment guide.

Update the config-dev.yaml properties appropriately and then use one of the following scripts to deploy the application to CloudHub:

• packageDeploy.sh (Mac/Linux)
• packageDeploy.cmd (Windows)

Testing

• Use Advanced Rest Client or Postman to send request over HTTP. The template includes a postman collection in src/test/resources folder. Update the collection variable(s) after successful import.